System and method for generating embeddable widgets which enable access to a cloud-based collaboration platform

ABSTRACT

Techniques are disclosed for generating embeddable widgets capable of accessing contents in a cloud-based platform. In one embodiment, a method comprises receiving a request identifying a target content in the cloud-based platform. The method further comprises automatically generating a plurality of software codes which correspond to a software widget that enables access to the target content. According to some embodiments, the software widget is to be embedded in a software product so as to enable a user of the software product to access the target content without navigating away from the software product. Among other advantages, embodiments disclosed herein provide easy integration of centralized contents to users and third-party web-service vendors, and reduce the effort necessary for system administrators in controlling data security and tracking different activities performed to the centralized content, thereby enabling more intuitive user experience without sacrificing data security.

CROSS-REFERENCE TO RELATED APPLICATIONS AND EFFECTIVE FILING DATEENTITLEMENT

This application is entitled to the benefit of and the right of priorityto U.S. Provisional Patent Application No. 61/710,182, entitled“EMBEDDED HTML FOLDER WIDGET FOR ACCESSING A CLOUD COLLABORATIONPLATFORM AND CONTENT FROM ANY SITE”, filed Oct. 5, 2012, which is herebyincorporated by reference in its entirety. This application is thereforeentitled to an effective filing date of Oct. 5, 2012.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the United States Patent andTrademark Office patent files or records, but otherwise reserves allcopyright rights whatsoever. The following notice applies to thesoftware and data as described below and in the drawings that form apart of this document: Copyright 2013, Box, Inc., All Rights Reserved.

BACKGROUND

With the advancements in digital technologies, data proliferation andthe ever increasing mobility of user platforms have created enormousamounts of information traffic over mobile and computer networks. Thisis particularly relevant to the increase of electronic and digitalcontents being used and shared over the network in social settings andworking environments as compared to traditional stand-alone personalcomputers and mobile devices. As a result, contents are shared acrossmultiple devices among multiple users.

Moreover, the concept of cloud computing has changed many ways how dataare stored and shared. Webpages now can provide much richerfunctionalities than their predecessors which may only be able to conveytext-based information. Thus, the traditional boundaries separatingsoftware applications, data storage, and web-based services graduallybecome obscure. However, there is still a need for improved ways thatcan provide better integration and more intuitive user experiencewithout sacrificing data security.

BRIEF DESCRIPTION OF DRAWINGS

The present embodiments are illustrated by way of example and are notintended to be limited by the figures of the accompanying drawings. Inthe drawings:

FIG. 1 depicts an example diagram of a system having a host server of acloud service, collaboration and/or cloud storage accounts withcapabilities that generate embeddable widgets capable of accessingcontents in a cloud-based platform;

FIG. 2 depicts an example diagram of a web-based or online collaborationplatform deployed in an enterprise or other organizational setting fororganizing work items and workspaces;

FIG. 3 depicts an example diagram of a workspace in an online orweb-based collaboration environment accessible by multiple collaboratorsthrough various devices;

FIG. 4 depicts a block diagram illustrating an example of components ina host server with capabilities that generate embeddable widgets capableof accessing contents in a cloud-based platform;

FIG. 5A-5C respectively depict screenshots showing example userinterfaces embodying one or more techniques disclosed herein forgenerating embeddable widgets capable of accessing a file in acloud-based platform;

FIG. 6A-6C respectively depict screenshots showing example userinterfaces embodying one or more techniques disclosed herein forgenerating embeddable widgets capable of accessing a folder in acloud-based platform;

FIG. 7 depicts a flowchart illustrating an example process forgenerating embeddable widgets capable of accessing contents in acloud-based platform; and

FIG. 8 depicts a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, can be executed.

The same reference numbers and any acronyms identify elements or actswith the same or similar structure or functionality throughout thedrawings and specification for ease of understanding and convenience.

DETAILED DESCRIPTION

Techniques are disclosed for generating embeddable widgets capable ofaccessing contents in a cloud-based platform. In one embodiment, amethod comprises receiving a request identifying a target content in thecloud-based platform. The method further comprises automaticallygenerating a plurality of software codes which correspond to a softwarewidget that enables access to the target content. According to someembodiments, the software widget is to be embedded in a software productso as to enable a user of the software product to access the targetcontent without navigating away from the software product.

Among other advantages, embodiments disclosed herein provide easyintegration of centralized contents to users and third-party web-servicevendors, and reduce the effort necessary for system administrators incontrolling data security and tracking different activities performed tothe centralized content, thereby enabling more intuitive user experiencewithout sacrificing data security.

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding of the disclosure. However, in certaininstances, well-known or conventional details are not described in orderto avoid obscuring the description. References to one or an embodimentin the present disclosure can be, but not necessarily are, references tothe same embodiment; and, such references mean at least one of theembodiments.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which can be exhibited by some embodiments and not by others.Similarly, various requirements are described which can be requirementsfor some embodiments but not other embodiments.

The terms used in this specification generally have their ordinarymeanings in the art, within the context of the disclosure, and in thespecific context where each term is used. Certain terms that are used todescribe the disclosure are discussed below, or elsewhere in thespecification, to provide additional guidance to the practitionerregarding the description of the disclosure. For convenience, certainterms can be highlighted, for example using italics and/or quotationmarks. The use of highlighting has no influence on the scope and meaningof a term; the scope and meaning of a term is the same, in the samecontext, whether or not it is highlighted. It will be appreciated thatsame thing can be said in more than one way.

Consequently, alternative language and synonyms can be used for any oneor more of the terms discussed herein, nor is any special significanceto be placed upon whether or not a term is elaborated or discussedherein. Synonyms for certain terms are provided. A recital of one ormore synonyms does not exclude the use of other synonyms. The use ofexamples anywhere in this specification including examples of any termsdiscussed herein is illustrative only, and is not intended to furtherlimit the scope and meaning of the disclosure or of any exemplifiedterm. Likewise, the disclosure is not limited to various embodimentsgiven in this specification.

Without intent to limit the scope of the disclosure, examples ofinstruments, apparatus, methods and their related results according tothe embodiments of the present disclosure are given below. Note thattitles or subtitles can be used in the examples for convenience of areader, which in no way should limit the scope of the disclosure. Unlessotherwise defined, all technical and scientific terms used herein havethe same meaning as commonly understood by one of ordinary skill in theart to which this disclosure pertains. In the case of conflict, thepresent document, including definitions will control.

FIG. 1 illustrates an example diagram of a system 100 having a hostserver 110 of a cloud service/platform, collaboration and/or cloudstorage service with capabilities that that generate embeddable widgetscapable of accessing contents in a cloud-based platform.

The client devices 102 can be any system and/or device, and/or anycombination of devices/systems that is able to establish a connection,including wired, wireless, cellular connections with another device, aserver and/or other systems such as host server 110 and/or a third-partyapplication 120. Client devices 102 typically include a display and/orother output functionalities to present information and data exchangedbetween/among the devices 102, the third-party application 120, and/orthe host server 110.

For example, the client devices 102 can include mobile, hand held orportable devices or non-portable devices and can be any of, but notlimited to, a server desktop, a desktop computer, a computer cluster, orportable devices including, a notebook, a laptop computer, a handheldcomputer, a palmtop computer, a mobile phone, a cell phone, a PDA, asmart phone (e.g., a BlackBerry device such as BlackBerry Z10/Q10, aniPhone, Nexus 4, etc.), a Treo, a handheld tablet (e.g. an iPad, iPadMini, a Galaxy Note, Galaxy Note II, Xoom Tablet, Microsoft Surface,Blackberry PlayBook, Nexus 7, 10 etc.), a phablet (e.g., HTC Droid DNA,etc.), a tablet PC, a thin-client, a hand held console, a hand heldgaming device or console (e.g., XBOX live, Nintendo DS, Sony PlayStationPortable, etc.), iOS powered watch, Google Glass, a Chromebook and/orany other portable, mobile, hand held devices, etc. running on anyplatform or any operating system (e.g., Mac-based OS (OS X, iOS, etc.),Windows-based OS (Windows Mobile, Windows 7, Windows 8, etc.), Android,Blackberry OS, Embedded Linux platforms, Palm OS, Symbian platform,Google Chrome OS, and the like. In one embodiment, the client devices102, and host server 110 are coupled via a network 106. In someembodiments, the devices 102 and host server 110 can be directlyconnected to one another.

The input mechanism on client devices 102 can include touch screenkeypad (including single touch, multi-touch, gesture sensing in 2D or3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motiondetector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), alight sensor, capacitance sensor, resistance sensor, temperature sensor,proximity sensor, a piezoelectric device, device orientation detector(e.g., electronic compass, tilt sensor, rotation sensor, gyroscope,accelerometer), or a combination of the above.

Signals received or detected indicating user activity at client devices102 through one or more of the above input mechanism, or others, can beused by various users or collaborators (e.g., collaborators 108) foraccessing, through network 106, a web-based collaboration environment oronline collaboration platform (e.g., hosted by the host server 110). Thecollaboration environment or platform can have one or more collectivesettings 105 for an enterprise or an organization that the users belong,and can provide an user interface 104 (e.g., via a webpage applicationaccessible by the web browsers of devices 102) for the users to accesssuch platform under the settings 105. Additionally, a client softwarethat is native to the cloud collaboration platform can be provided(e.g., through downloading from the host server 110 via the network 106)to run on the client devices 102 to provide cloud-based platform accessfunctionalities. The users and/or collaborators can access thecollaboration platform via a client software user interface 107, whichcan be provided by the execution of the client software on the devices102.

The collaboration platform or environment hosts workspaces with workitems that one or more users can access (e.g., view, edit, update,revise, comment, download, preview, tag, or otherwise manipulate, etc.).A work item can generally include any type of digital or electroniccontent that can be viewed or accessed via an electronic device (e.g.,device 102). The digital content can include .pdf files, .doc, slides(e.g., Powerpoint slides), images, audio files, multimedia content, webpages, blogs, etc. A workspace can generally refer to any grouping of aset of digital content in the collaboration platform. The grouping canbe created, identified, or specified by a user or through other means.This user can be a creator user or administrative user, for example.

In general, a workspace can be associated with a set of users orcollaborators (e.g., collaborators 108) which have access to the contentincluded therein. The levels of access (e.g., based on permissions orrules) of each user or collaborator to access the content in a givenworkspace can be the same or can vary among the users. Each user canhave their own set of access rights to every piece of content in theworkspace, or each user can be different access rights to differentpieces of content. Access rights can be specified by a user associatedwith a workspace and/or a user who created/uploaded a particular pieceof content to the workspace, or any other designated user orcollaborator.

In general, the collaboration platform allows multiple users orcollaborators to access or collaborate efforts on work items such eachuser can see, remotely, edits, revisions, comments, or annotations beingmade to specific work items through their own user devices. For example,a user can upload a document to a workspace for other users to access(e.g., for viewing, editing, commenting, signing-off, or otherwisemanipulating). The user can login to the online platform and upload thedocument (or any other type of work item) to an existing workspace or toa new workspace. The document can be shared with existing users orcollaborators in a workspace.

In general, network 106, over which the client devices 102 and the hostserver 110 communicate can be a cellular network, a telephonic network,an open network, such as the Internet, or a private network, such as anintranet and/or the extranet, or any combination or variation thereof.For example, the Internet can provide file transfer, remote log in,email, news, RSS, cloud-based services, instant messaging, visualvoicemail, push mail, VoIP, and other services through any known orconvenient protocol, such as, but is not limited to the TCP/IP protocol,Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH,RS-232, SDH, SONET, etc.

The network 106 can be any collection of distinct networks operatingwholly or partially in conjunction to provide connectivity to the clientdevices 102 and the host server 110 and can appear as one or morenetworks to the serviced systems and devices. In one embodiment,communications to and from the client devices 102 can be achieved by, anopen network, such as the Internet, or a private network, such as anintranet and/or the extranet. In one embodiment, communications can beachieved by a secure communications protocol, such as secure socketslayer (SSL), or transport layer security (TLS).

In addition, communications can be achieved via one or more networks,such as, but are not limited to, one or more of WiMax, a Local AreaNetwork (LAN), Wireless Local Area Network (WLAN), a Personal areanetwork (PAN), a Campus area network (CAN), a Metropolitan area network(MAN), a Wide area network (WAN), a Wireless wide area network (WWAN),enabled with technologies such as, by way of example, Global System forMobile Communications (GSM), Personal Communications Service (PCS),Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, FixedWireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE,LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks,enhanced data rates for GSM evolution (EDGE), General packet radioservice (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA,UMTS-TDD, 1×RTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS,extensible messaging and presence protocol (XMPP), real time messagingprotocol (RTMP), instant messaging and presence protocol (IMPP), instantmessaging, USSD, IRC, or any other wireless data networks or messagingprotocols.

Third-party applications 120 may be provided by third-party softwareapplication vendors and may be accessible to the users via the network106. For example, third-party applications 120 can be provided throughwebpages provided from servers hosted by the third-party softwareapplication vendors using the Internet; for another example, third-partyapplications 120 can be provided using webpages that are operated by aserver serving an intranet (e.g., within a corporate setting).Additionally, third-party applications 120 can also be provided via,after download (and installation if required), software codes (e.g.,applications) running on the user devices 102. In any of the aboveconfigurations, the third-party applications 120 may communicate withthe host server 110 for accessing cloud-based collaboration platform,storage and/or services in performing their functions, such as theembeddable widget generation techniques further discussed herein.

The embodiments disclosed herein recognize that conventional ways ofsharing contents stored in the cloud would require either the usersvisiting a webpage interface (e.g., interface 104) or a client softwareuser interface (e.g., interface 107) to access the contents. This maycreate an unpleasant user experience as the users may be required toleave or navigate away from the software applications (whether it isprovided through the Internet, intranet, or other suitable sources) thatthey are currently using in order to gain the access, and/or the usersmay be required to install and execute a software or a plug-in that isforeign to their systems.

Accordingly, the present disclosure provides intuitive and easy ways toenable access to contents in the cloud-based platform within third-partyapplications 120, and especially when the third-party applications 120are web-based (e.g., via a webpage), thereby improving user experiencethrough better integration, alleviating workload for the administratorson tracking activities and maintaining data security, as well asreducing deployment time for the developers of the third-partyapplications 120 to integrate such functionalities.

More specifically, some embodiments of the host server 110 can utilizecross-platform computer languages (e.g., HyperText Markup Language(HTML) such as HTML5) to generate software codes which correspond to asoftware widget that enable access to contents in the cloud-basedplatform. The software widget may be embedded in a software product(e.g., a webpage, a web application or other suitable web-basedservices) so as to enable a user of the software product to access thecontents without navigating away from the software product. For purposesof discussion herein, a “software widget” or a “widget” represents atype of computer software that typically comprises portable softwarecodes capable of being executed in one or more different softwareplatforms; therefore, it is noted that, although the present embodimentsare particularly useful to implement web widgets that are included inwebpages (e.g., that are HTML-based), the techniques disclosed hereincan be similarly applied to other suitable kinds of widgets including,for example, a graphic user interface (GUI) widget, a desktop widget, ameta-widget, a widget application, and the like.

For example, the generated software codes, when included in a webpageprovided by the third-party applications 120 and executed by a webbrowser on the user devices 102, can create an embedded widget withinthe webpage of the third-party applications 120 which provide selectfunctionalities similar to those of the applications native to thecloud-based platform. The software widget can enable features including,for example, preview, file uploading (e.g., into repository 130), realtime updates, editing, commenting and collaborator management. Thedisclosed techniques can allow customers, developers, as well as otherpartners of the developers to collaborate on centralized andsynchronized contents, regardless of different location they may be inand different system they may employ. Additionally or alternatively, asthe cloud-based platform adds more functionalities and/or collaborationfeatures, the software widget can automatically receive these additionalfunctions/features. For example, as the user adds new files to thefolder (e.g., in the cloud-based platform) associated with a softwarewidget, the new files can appear in the widget automatically.

In this way, among other benefits, the present embodiments can save timeand increase productivity for the users by enabling them to accesscontents (e.g., files or folders) within the third-party applications120 (e.g., embedded in an interface webpage of applications 120) thatthey are using, with requiring the users to navigate away or leave theapplications 120. Further, the present embodiments can keep the accessedcontents and discussions (e.g., comments, or highlights) centralized inthe cloud-based platform. Still further, the present embodiments canallow administrators to keep the accessed contents centralized andsecured in the cloud-based platform. The administrators can also selectpermission levels (e.g., for different instances of software widgetswhich may gain access to the same content), perform activitytracking/reporting, or adjust other suitable management and securityoptions. Developers of the third-party applications 120 can now embedthe software widget (e.g., as generated by the host server 110 usingtechniques disclosed herein) to any third-party applications (e.g., byincluding the generated HTML5 codes in their webpages) in a relativelyshort period of time, thus reducing the engineering workload whenbuilding an application base on the cloud-based platform.

More implementation details on the software code generation techniqueswhich can be implemented on the host server 110 to render softwarewidgets on webpages or other interfaces of third-party applications 120are discussed in fuller detail below, and particularly with regard toFIG. 4.

FIG. 2 depicts an example diagram of a web-based/cloud-based or onlinecollaboration platform deployed in an enterprise or other organizationalsetting 250 for organizing work items 215, 235, 255 and workspaces 205,225, 245.

The web-based platform for collaborating on projects or jointly workingon documents can be used by individual users and shared amongcollaborators. In addition, the collaboration platform can be deployedin an organized setting including but not limited to, a company (e.g.,an enterprise setting), a department in a company, an academicinstitution, a department in an academic institution, a class or coursesetting, or any other types of organizations or organized setting.

When deployed in an organizational setting, multiple workspaces (e.g.,workspace A, B C) can be created to support different projects or avariety of work flows. Each workspace can have its own associate workitems. For example, workspace A 205 can be associated with work items215, workspace B 225 can be associated with work items 235, andworkspace N can be associated with work items 255. The work items 215,235, and 255 can be unique to each workspace but need not be. Forexample, a particular word document can be associated with only oneworkspace (e.g., workspace A 205) or it can be associated with multipleworkspaces (e.g., Workspace A 205 and workspace B 225, etc.).

In general, each workspace has a set of users or collaboratorsassociated with it. For example, workspace A 205 is associated withmultiple users or collaborators 206. In some instances, workspacesdeployed in an enterprise can be department specific. For example,workspace B can be associated with department 210 and some users shownas example user A 208 and workspace N 245 can be associated withdepartments 212 and 216 and users shown as example user B 214.

Each user associated with a workspace can generally access the workitems associated with the workspace. The level of access will depend onpermissions associated with the specific workspace, and/or with aspecific work item. Permissions can be set for the workspace or setindividually on a per work item basis. For example, the creator of aworkspace (e.g., one of user A 208 who creates workspace B) can set onepermission setting applicable to all work items 235 for other associatedusers and/or users associated with the affiliate department 210, forexample. Creator user A 208 can also set different permission settingsfor each work item, which can be the same for different users, orvarying for different users.

In each workspace A, B . . . N, when an action is performed on a workitem by a given user or any other activity is detected in the workspace,other users in the same workspace can be notified (e.g., in real time orin near real time, or not in real time). Activities which trigger realtime notifications can include, by way of example but not limitation,adding, deleting, or modifying collaborators in the workspace,uploading, downloading, adding, deleting a work item in the workspace,creating a discussion topic in the workspace.

In some embodiments, items or content downloaded or edited can causenotifications to be generated. Such notifications can be sent torelevant users to notify them of actions surrounding a download, anedit, a change, a modification, a new file, a conflicting version, anupload of an edited or modified file.

In one embodiment, in a user interface to the web-based collaborationplatform where notifications are presented, users can, via the sameinterface, create action items (e.g., tasks) and delegate the actionitems to other users including collaborators pertaining to a work item215, for example. The collaborators 206 can be in the same workspace A205 or the user can include a newly invited collaborator. Similarly, inthe same user interface where discussion topics can be created in aworkspace (e.g., workspace A, B or N, etc.), actionable events on workitems can be created and/or delegated/assigned to other users such ascollaborators of a given workspace 206 or other users. Through the sameuser interface, task status and updates from multiple users orcollaborators can be indicated and reflected. In some instances, theusers can perform the tasks (e.g., review or approve or reject, etc.)via the same user interface.

FIG. 3 depicts an example diagram of a workspace 302 in an online orweb-based collaboration environment accessible by multiple collaborators322 through various devices.

Each of users 316, 318, and 320 can individually use multiple differentdevices to access and/or manipulate work items 324 in the workspace 302with which they are associated with. For example users 316, 318, 320 canbe collaborators on a project to which work items 324 are relevant.Since the work items 324 are hosted by the collaboration environment(e.g., a cloud-based environment), each user can access the work items324 anytime, and from any physical location using any device (e.g.,including devices they own or any shared/public/loaner device).

Work items to be edited or viewed can be accessed from the workspace302. Users can also be notified of access, edit, modification, and/orupload related-actions performed on work items 324 by other users or anyother types of activities detected in the workspace 302. For example, ifuser 316 modifies a document, one or both of the other collaborators 318and 320 can be notified of the modification in real time, or nearreal-time, or not in real time. The notifications can be sent throughany of all of the devices associated with a given user, in variousformats including, one or more of, email, SMS, or via a pop-up window ina user interface in which the user uses to access the collaborationplatform. In the event of multiple notifications, each notification canbe depicted preferentially (e.g., ordering in the user interface) basedon user preferences and/or relevance to the user (e.g., implicit orexplicit).

For example, a notification of a download, access, read, write, edit, oruploaded related activities can be presented in a feed stream amongother notifications through a user interface on the user deviceaccording to relevancy to the user determined based on current or recentactivity of the user in the web-based collaboration environment.

In one embodiment, the notification feed stream further enables users tocreate or generate actionable events (e.g., as task) which are or can beperformed by other users 316 or collaborators 322 (e.g., including adminusers or other users not in the same workspace), either in the sameworkspace 302 or in some other workspace. The actionable events such astasks can also be assigned or delegated to other users via the same userinterface.

For example, a given notification regarding a work item 324 can beassociated with user interface features allowing a user 316 to assign atask related to the work item 324 (e.g., to another user 316, admin user318, creator user 320 or another user). In one embodiment, a commentinguser interface or a comment action associated with a notification can beused in conjunction with user interface features to enable taskassignment, delegation, and/or management of the relevant work item orwork items in the relevant workspaces, in the same user interface.

FIG. 4 depicts a block diagram illustrating an example of components ina host server 400 (e.g., server 110, FIG. 1) with capabilities that thatgenerate embeddable widgets capable of accessing contents in acloud-based platform. The widget can be embedded in, for example, awebpage rendered by a browser (e.g., running on devices 102), or anapplication operating on a mobile device 102. With additional referenceto FIGS. 1-3, the software widget generation techniques which the hostserver 400 can employ are described. The cloud-based platform can beshared between a vendor user 316 (FIG. 3) and collaborators 322 (FIG. 3)of the user 316.

The host server 400 of the web-based or online collaboration environmentcan generally be a cloud-based service. The host server 400 can include,for example, a network interface 410, a widget generation engine 420having a configuration parameter module 430 and a source code generatormodule 435, and a content access controller 440. In some embodiments ofthe host server 400, the configuration parameter module 430 furtherincludes a layout customization module 432 a, a function customizationmodule 432 b, and a permission control module 432 c. One or moreembodiments of the content access controller 440 can include, forexample, a download module 442 and an upload controller 444.

As used herein, a “module,” “a manager,” an “interface,” or an “engine”includes a general purpose, dedicated or shared processor and,typically, firmware or software modules that are executed by theprocessor. Depending upon implementation-specific or otherconsiderations, the module, manager, interface, or engine can becentralized or its functionality distributed. The module, manager,interface, or engine can include general or special purpose hardware,firmware, or software embodied in a computer-readable (storage) mediumfor execution by the processor. As used herein, a computer-readablemedium or computer-readable storage medium is intended to include allmedia that are statutory (e.g., in the United States, under 35 U.S.C.§101), and to specifically exclude all media that are non-statutory innature to the extent that the exclusion is necessary for a claim thatincludes the computer-readable (storage) medium to be valid. Knownstatutory computer-readable mediums include hardware (e.g., registers,random access memory (RAM), non-volatile (NV) storage, to name a few),but may or may not be limited to hardware.

The network interface 410 can be a networking module that enables thehost server 400 to mediate data in a network with an entity that isexternal to the host server 400, through any known and/or convenientcommunications protocol supported by the host and the external entity.The network interface 410 can include one or more of a network adaptorcard, a wireless network interface card (e.g., SMS interface, WiFiinterface, interfaces for various generations of mobile communicationstandards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.),Bluetooth, a router, an access point, a wireless router, a switch, amultilayer switch, a protocol converter, a gateway, a bridge, bridgerouter, a hub, a digital media receiver, and/or a repeater.

As previously described, overall, the host server 400 can generate(e.g., in response to an embedding request) software codes whichcorrespond to a software widget that enable access to contents in thecloud-based platform.

More specifically, in some embodiments, the host server 400 can receive(e.g., via the network interface 410) an embedding request identifying atarget content (e.g., a work item 324, FIG. 3, such as a file or afolder) in the cloud-based platform (e.g., workspace 302, FIG. 3).Afterwards, the widget generation engine 420 of the host server 400 canautomatically generate (e.g., via the source code generator module 435)a plurality of software codes which correspond to a software widget thatenables access to the target content. In one or more embodiments, thesoftware widget may be embedded in a third-party software product (e.g.,a webpage, a web application or other suitable web-based services, suchas third-party applications 120, FIG. 1) so as to enable a customer userof the software product to access the contents without leaving ornavigating away from the software product. In other words, the customeruser can access the target content simply by using the interface (e.g.,in forms of webpages) provided by the third-party software product,without the need of leaving the software product and without the need ofusing native cloud-based platform interfaces such as interfaces 104 and107 (FIG. 1) in order to gain the access. The vendors of the third-partyapplications 120 can also enjoy better control over the contents towhich the customer user has access.

In some embodiments, to utilize the host server 400's widget generationfunctionalities, the embedding request can be received from a user(e.g., a vendor of the third-party applications 120) by using widgetgeneration interfaces provided by the host server 400 in, for example,interfaces 104. FIGS. 5A-5C respectively depict screenshots showingexample user interfaces 500, 502, and 504 which are embodiments of thewidget generation interfaces for generating embeddable widgets capableof accessing a file in a cloud-based platform.

As illustrated in FIG. 5A, a widget generation interface 500 (e.g.,which is displayed in the web browser of the users device 102) can beoperated by the user in generating software codes that correspond tosoftware widgets. In some embodiments, the generated software codescorresponding to the widgets can be executed, for example, in a webbrowser of user devices (e.g., devices 102, FIG. 1). In one or moreembodiments, the software codes can be executed by the web browsernatively (e.g., so that a plug-in is not required). An example type ofthe software codes is HTML5. As such, the software codes are configuredto be directly included in a software product (e.g., by copying theHTML5 code into the webpage of the third-party applications 120) withouta compilation process. According to some embodiments, the generatedsoftware codes can be used to embed a software widget that accessestarget contents into the third-party vendor user's website or blog. Someexamples of the access to the target content can include viewing thecontents of a file, whereas the widget can be an embedded reader thatshows pages of a document file, an embedded image viewer that showsimages from a photo file, or an embedded media player that plays musicin an audio file or video frames from a video file, etc.

More specifically, to embed a file in a webpage, the user can firstlocate the file in the cloud-based platform or in workspace 302 usingthe interface 500 (e.g., interface 104). The interface 500 includes amenu button (e.g., button 510), and the user can generate the embeddingrequest by choosing to activate the “Embed file in your site” functionfrom a “Share” submenu under the menu. The host server 400 receives thisrequest, and can generate another widget generation interface (e.g., apop-up window such as interface 502 of FIG. 5B) where the user canadjust or enter configuration parameters to customize the embeddablewidget. The adjustments of configuration parameters can be received bythe configuration parameter module 430, and the source code (e.g.,HTML5) generator module 435 can generate and/or adjust the embeddablecomputer code accordingly. The resulting computer code can be presentedto the user via the user interface 502 (e.g., in area 520, as shown inFIG. 5B).

According to some specific examples, the customization can includeslayout definitions for the software widget, such as size, height, width,or color theme of the widget. The layout definitions can be received bythe layout customization module 432 a for processing (e.g., for codegenerating in the code generator module 435). As illustrated in theexample of FIG. 5B, the user can change the size of the embedded widgetby adjusting the pixel numbers next to “Width” and “Height” as well aschange the background color of the software widget.

Additionally or alternatively, the customization can include adjustmentof functionalities of the software widget in accessing the targetcontent, such as adjusting permission levels, or different toolfunctionalities like print, write, edit and save back, share link,download access, copy and paste, etc. Additional functionalities thatcan be adjusted can include editing the file, commenting on the file,highlighting portions of the file, or sharing the file. The adjustmentcan be received by the function customization module 432 b and/or thepermission control module 432 c for processing (e.g., for codegenerating in the code generator module 435). As illustrated in theexample of FIG. 5B, the user can select the amount of access to thedocument the user wishes the user's customers to have by adjusting thecheck boxes on the right side of the interface 502. In this particularcase, the user can turn off the ability to print the document, turn offthe ability to download the document, as well as disable the customerusers from sharing a link to the file.

Further, in some embodiments, the widget generation engine 420 canprompt the user with an option to preview the software widget, and uponactivation of the option, the host server 400 can cause a web browser ofthe user to execute the software codes so as to generate the softwarewidget in, for example, a new webpage. In the example illustrated inFIG. 5B, the user can preview the customized embeddable widget bychoosing a ‘Preview this embed’ function 530, and a new interface can bedisplayed (e.g., as a pop-up window, as a new webpage, or the like) toshow an actual software widget as populated by the web browser based onthe generated computer code. Such preview of the actual software widgetis shown in widget preview interface 504 of FIG. 5C. In this way, thevendor user can verify the software widget's functionalities, layout,and in some embodiments, different permission settings.

The widget generation engine 420 can prompt the user to copy thesoftware codes into a memory on a device of the user. For the exampleshown in FIG. 5B, the vendor user can choose a “Copy to Clipboard”function 540 to copy the computer code (e.g., in forms of HTML) to aclipboard (e.g., a temporary cache memory) of the user's device. Assuch, after the user becomes satisfied with the look and feel of thesoftware widget, the user can copy and paste the computer codes into alocation (e.g., a webpage) of the vendor's own desire that allows customHTML widget to be embedded.

It is noted that, in some embodiments, the software codes are uniquelygenerated by the source code generator module 435 so that differentsoftware widgets generated in a plurality of instances can access theidentified target content and each have a distinct configuration. Insome of these embodiments, each time the vendor user activates the“Embed file in your site” option, a unique instance of the widget can becreated. This technique can allow the vendor user to create multipleembedded instances of the same target content (e.g., a single document),and each embedded instance of software widget can have its own customaccess and size settings. In an additional or alternative embodiment,the vendor user can change the settings of an existing embedded widgetby generating a new widget for the file or content with the settings theuser so desires, and replace the old computer codes included in theuser's computer product (e.g., a website).

Some examples of file types that the software widgets can view includeAdobe Acrobat (.pdf), Adobe Illustrator (.ai), Adobe Photoshop (.psd),CSV, HTML, Microsoft Excel (.xls, .xlsx), Microsoft Powerpoint (.ppt,.pptx), Microsoft Word (.doc, .docx), Open Office Presentation (.odp),Open Office Spreadsheet (.ods), Open Office Word Processing (.odt), RTF,TXT, Word Perfect (.wpd), JPEG, PNG, GIF, TIFF, BMP, FLV, SWF, MP3, andso forth. In some embodiments, if the target content (e.g., file) iseither not a supported file type, or if the vendor user do not havesufficient privileges to share that file, the widget generation engine420 does not display the option to embed the file to the user.

Furthermore, some other examples of the access to the target content caninclude viewing the contents of a folder, whereas the widget can be anembedded file manager that shows lists of files in the folder as well asa select number of other functions (as controlled by configurationparameter module 430) that a typical file manager can have. FIG. 6A-6Crespectively depict screenshots showing example user interfaces 600,602, and 604 for generating embeddable widgets capable of accessing afolder in a cloud-based platform.

More specifically, in addition or as an alternative to theaforementioned functionalities (e.g., with respect to embedding one ormore individual files) of the widget generation engine 420, the vendoruser can choose embed a folder of the cloud-based platform in, forexample, a website that supports HTML embed code.

In manners similar to the embodiments mentioned above, in someembodiments, the vendor user can first generate an embedding request toutilize the host server 400's widget generation functionalities. Asillustrated in FIG. 6A, a widget generation interface 600 (e.g., whichcan be displayed in the web browser of the users device 102) can beoperated by the user to generate the request. In the example shown inFIG. 6A, the user can click on a “Folder Options” function 610 in theinterface 600, select “Share,” and select “Embed Folder in Your Site” togenerate the embedding request to the host server 400.

The host server 400 receives (e.g., via the network interface 410) thisrequest, and can generate another widget generation interface (e.g., apop-up window such as interface 602 of FIG. 6B) where the user canadjust or enter configuration parameters to customize the layout and thefunctionalities of the embeddable widget. More specifically, similarlayout parameters (e.g., size, color, etc.) that are discussed above forsoftware widgets that access a file can be applicable (e.g., by thelayout customization module 432 a) to the software widgets that access afolder. With regard to functionality, in addition to displaying a listfiles in the folder, examples of functionalities that the user canadjust for the software widget that accesses the target folder caninclude enabling downloading a number of files from the folder, changinga sorting option (e.g., by name, size, type, date, tag, etc.) for thefiles in the folder, or changing a different view style (e.g., list,thumbnail, details, etc). The adjustment of functionalities can bereceived by the function customization module 432 b and/or thepermission control module 432 c. As mentioned, the source code generatormodule 435 generates computer codes based on the configurationparameters, and the widget generation engine 420 displays the generatedcomputer codes in an interface (e.g., area 620 of interface 602).

In some embodiments, the user can also preview the embedded folder byselecting a “Preview this embed” function, an example of which isillustrated as function 630. An example showing the “preview” of thesoftware widget that can access a folder is shown in interface 604 ofFIG. 6C. When the user finishes customizing, the user can select a “Copyto Clipboard” function 640 to copy the generated computer codes, andpaste the computer codes (e.g., HTML) in a desired location.

Additional or alternatively, the user can still edit an existing folderwidget after it has been embedded. In some embodiments, to edit anexisting embedded folder, the vendor user is required by the host server400 to log into his or her account first.

Still further, in some embodiments, the access to the target contentincludes uploading a file to the folder so that the user can acceptfiles by using the software widget. For example, the user can set up afolder in the cloud-based platform for other companies to submit bidsfor business, or the user may want to accept submissions for a writingcontest. Accordingly, the widget generation engine 420 can create asoftware widget with access to a folder and allowing people to uploadfiles directly to the user's shared folder.

In one or more embodiments, The user can first create a folder in thecloud-based platform for people to upload files, or alternatively, canchoose an existing folder. Although not shown for simplicity, in thecustomization interface 602, one of the configuration parameters can beallowing upload. Other appropriate settings such as permission level, orsecurity handling (e.g., whether to scan and/or quarantine a uploadedfile) can also be adjusted. The function customization module 432 b andthe permission control module 432 c receive these settings, and thesource code generator module 435 generates the computer codes based onall the selected/adjusted configuration parameters. After including(e.g., by copying and pasting) the code into the user's computer product(e.g., the vendor's website), the folder can receive files from theuser's customers. As new files and folders are uploaded, they can appearin the user's folder for review.

In some embodiments, the host server 400 can inspect the uploaded filesincluding, for example, scanning for virus, Trojan horses, or otherunwanted information. Further, one or more embodiments of the hostserver 400 can quarantine, submit to the user for review, or performother actions on the uploaded file in response to a result from theinspecting.

Also, upon a widget being used to access contents in the workspace 302,the content access controller 440 in the host server 400 can ensure thatno unauthorized access can be performed by the software widget. In oneexample, the download module 442 of the access controller 440 can trackwhat activities are performed on the target content at what time and bywhich performer. One or more embodiments provide that the accesscontroller 440 can keep track of different versions of the accessedcontent. Additionally, the access controller 440 may generate reports ofthe monitoring to an administrator of the system for review.

Moreover, in some embodiments, the upload module 444 of the contentaccess controller 440 can prevent another software widget from accessingthe uploaded file. Additionally, some embodiments of the upload module444 can prevent a software widget from accessing (e.g., viewing) filesother than the ones that are uploaded by the software widget itself. Inthis way, the customers of the user can only upload files, but are notbe able to view or access other contents of the folder through thesoftware widget.

FIG. 7 depicts a flowchart illustrating an example process 700 forgenerating embeddable widgets capable of accessing contents (e.g., afolder, a file, or other suitable work items 324, FIG. 3) in acloud-based platform (e.g., workspace 302, FIG. 3). The method 700 isperformed, for example, in a host server of the workspace 302 (e.g.,server 400, FIG. 4).

First, the host server 400 can receive (710) (e.g., via the networkinterface 410, FIG. 4) an embedding request identifying a work item 324in the workspace 302. Afterwards, the host server 400 can automaticallygenerate (720) (e.g., via the source code generator module 435, FIG. 4)a plurality of software codes which correspond to a software widget thatenables access to the target content.

In one or more embodiments, the software widget can be embedded (722) ina third-party software product such as a webpage, a web application orother suitable web-based services so as to enable a customer user of thewebpage to access the work item 324 without leaving or navigating awayfrom the webpage. In other words, the host server 400 enables thecustomer user to access the work item 324 by using the webpage (e.g., asprovided by a third-party vendor) without the need of leaving thewebpage.

Further, in some embodiments, the software codes are uniquely generated(724) by the host server 400 (e.g., using source code generator module435, FIG. 4) so that different software widgets generated in a pluralityof instances can access the same work item 324, and each instance ofsoftware widget can have a distinct configuration. In some of theseembodiments, each time the vendor user sends an embedding request to thehost server 400, a unique instance of the widget can be created by thehost server 400. This technique can allow the vendor user to createmultiple embedded instances of the same target content (e.g., a singledocument), and each embedded instance of software widget can have itsown custom access and size settings.

In an additional or alternative embodiment, the vendor user can changethe settings of an existing embedded widget by generating a new widgetfor the file or content with the settings the user so desires, andreplace the old computer codes included in the user's computer product(e.g., a website).

FIG. 8 shows a diagrammatic representation 800 of a machine in theexample form of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, can be executed.

In alternative embodiments, the machine operates as a standalone deviceor can be connected (e.g., networked) to other machines. In a networkeddeployment, the machine can operate in the capacity of a server or aclient machine in a client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment.

The machine can be a server computer, a client computer, a personalcomputer (PC), a user device, a tablet, a phablet, a laptop computer, aset-top box (STB), a personal digital assistant (PDA), a thin-clientdevice, a cellular telephone, an iPhone, an iPad, a Blackberry, aprocessor, a telephone, a web appliance, a network router, switch orbridge, a console, a hand-held console, a (hand-held) gaming device, amusic player, any portable, mobile, hand-held device, or any machinecapable of executing a set of instructions (sequential or otherwise)that specify actions to be taken by that machine.

While the machine-readable medium or machine-readable storage medium isshown in an exemplary embodiment to be a single medium, the term“machine-readable medium” and “machine-readable storage medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” and “machine-readable storage medium” shallalso be taken to include any medium that is capable of storing, encodingor carrying a set of instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies of thepresently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of thedisclosure, can be implemented as part of an operating system or aspecific application, component, program, object, module or sequence ofinstructions referred to as “computer programs.” The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processing units or processors in acomputer, cause the computer to perform operations to execute elementsinvolving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fullyfunctioning computers and computer systems, those skilled in the artwill appreciate that the various embodiments are capable of beingdistributed as a program product in a variety of forms, and that thedisclosure applies equally regardless of the particular type of machineor computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readablemedia, or computer-readable (storage) media include, but are not limitedto, recordable type media such as volatile and non-volatile memorydevices, floppy and other removable disks, hard disk drives, opticaldisks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital VersatileDisks, (DVDs), etc.), among others, and transmission type media such asdigital and analog communication links.

The network interface device enables the machine 2800 to mediate data ina network with an entity that is external to the host server, throughany known and/or convenient communications protocol supported by thehost and the external entity. The network interface device can includeone or more of a network adaptor card, a wireless network interfacecard, a router, an access point, a wireless router, a switch, amultilayer switch, a protocol converter, a gateway, a bridge, bridgerouter, a hub, a digital media receiver, and/or a repeater.

The network interface device can include a firewall which can, in someembodiments, govern and/or manage permission to access/proxy data in acomputer network, and track varying levels of trust between differentmachines and/or applications. The firewall can be any number of moduleshaving any combination of hardware and/or software components able toenforce a predetermined set of access rights between a particular set ofmachines and applications, machines and machines, and/or applicationsand applications, for example, to regulate the flow of traffic andresource sharing between these varying entities. The firewall canadditionally manage and/or have access to an access control list whichdetails permissions including for example, the access and operationrights of an object by an individual, a machine, and/or an application,and the circumstances under which the permission rights stand.

Other network security functions can be performed or included in thefunctions of the firewall, can be, for example, but are not limited to,intrusion-prevention, intrusion detection, next-generation firewall,personal firewall, etc. without deviating from the novel art of thisdisclosure.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof, means any connection or coupling,either direct or indirect, between two or more elements; the coupling ofconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, shall referto this application as a whole and not to any particular portions ofthis application. Where the context permits, words in the above DetailedDescription using the singular or plural number can also include theplural or singular number respectively. The word “or,” in reference to alist of two or more items, covers all of the following interpretationsof the word: any of the items in the list, all of the items in the list,and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is notintended to be exhaustive or to limit the teachings to the precise formdisclosed above. While specific embodiments of, and examples for, thedisclosure are described above for illustrative purposes, variousequivalent modifications are possible within the scope of thedisclosure, as those skilled in the relevant art will recognize. Forexample, while processes or blocks are presented in a given order,alternative embodiments can perform routines having steps, or employsystems having blocks, in a different order, and some processes orblocks can be deleted, moved, added, subdivided, combined, and/ormodified to provide alternative or subcombinations. Each of theseprocesses or blocks can be implemented in a variety of different ways.Also, while processes or blocks are at times shown as being performed inseries, these processes or blocks can instead be performed in parallel,or can be performed at different times. Further, any specific numbersnoted herein are only examples: alternative implementations can employdiffering values or ranges.

The teachings of the disclosure provided herein can be applied to othersystems, not necessarily the system described above. The elements andacts of the various embodiments described above can be combined toprovide further embodiments.

Any patents and applications and other references noted above, includingany that can be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the disclosure can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further embodiments of thedisclosure.

These and other changes can be made to the disclosure in light of theabove Detailed Description. While the above description describescertain embodiments of the disclosure, and describes the best modecontemplated, no matter how detailed the above appears in text, theteachings can be practiced in many ways. Details of the system can varyconsiderably in its implementation details, while still beingencompassed by the subject matter disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the disclosure should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the disclosure with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the disclosure to the specific embodimentsdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe disclosure encompasses not only the disclosed embodiments, but alsoall equivalent ways of practicing or implementing the disclosure underthe claims.

While certain aspects of the disclosure are presented below in certainclaim forms, the inventors contemplate the various aspects of thedisclosure in any number of claim forms. For example, while only oneaspect of the disclosure is recited as a means-plus-function claim under35 U.S.C. §112, ¶ 6, other aspects can likewise be embodied as ameans-plus-function claim, or in other forms, such as being embodied ina computer-readable medium. (Any claim intended to be treated under 35U.S.C. §112, ¶ 6 begins with the words “means for”.) Accordingly, theapplicant reserves the right to add additional claims after filing theapplication to pursue such additional claim forms for other aspects ofthe disclosure.

What is claimed is:
 1. A method for enabling access to a cloud-basedplatform, the method comprising: receiving a request identifying atarget content that is shareable between a user and one or morecollaborators of the user in the cloud-based platform, wherein therequest includes customizable functionalities associated with one ormore available types of access around the target content; automaticallygenerating, by the cloud-based platform and based on said request,embeddable software code that is embeddable in one or more softwareproducts for generating a software widget to provide access to thetarget content from the one or more software products that are differentfrom the cloud-based platform generating the software code, whereingenerating the embeddable software code includes: receiving a userselection of a folder in the cloud-based platform to be embedded in thesoftware widget, the folder being accessible through the software widgetand in the cloud-based platform, receiving configuration parameters, theconfiguration parameters configuring the software widget to instruct thecloud-based platform to perform security related tasks on a fileuploaded to the folder via the software widget, the security relatedtasks including scanning and/or quarantining the file, and generatingthe embeddable software code based on the user selection and theconfiguration parameters; transmitting the embeddable software code to auser device associated with the user; receiving an indication at thecloud-based platform that the embeddable software code is embedded in asoftware product of the one or more software products; and generatingthe software widget in the software product in response to theembeddable software code being embedded in the software product, whereinsaid software widget provides the one or more available types of accessto the target content in accordance with the customizablefunctionalities included in the request.
 2. The method of claim 1,wherein the software widget is configured to enable a user of thesoftware product to access the target content without navigating awayfrom the software product.
 3. The method of claim 1, wherein thesoftware widget is generated as a unique instance.
 4. The method ofclaim 1, wherein the embeddable software code are uniquely generated sothat different software widgets generated in a plurality of instancescan access the identified target content and each have a distinctconfiguration.
 5. The method of claim 1, further comprising: prompting auser to preview the software widget, wherein activation of the previewcauses a web browser of the user to execute the software embeddablecode.
 6. The method of claim 1, further comprising: prompting a user tocopy the embeddable software code into a memory on a device of the user.7. The method of claim 1, wherein the embeddable software code areconfigured to be directly included in the software product without acompilation process.
 8. The method of claim 7, wherein the softwareproduct is a webpage or a web application.
 9. The method of claim 1,wherein the request is received from a user, the method furthercomprising: presenting, via a user interface, the embeddable softwarecode to the user.
 10. The method of claim 1, wherein the target contentcomprises a file, and wherein the access to the target content includesviewing the file.
 11. The method of claim 10, wherein the access to thetarget content further includes one or more of: editing the file,commenting on the file, highlighting portions of the file, or sharingthe file, or a combination thereof.
 12. The method of claim 1, whereinthe target content comprises a folder, and wherein the access to thetarget content includes displaying a list of work items in the folder.13. The method of claim 12, wherein the access to the target contentfurther includes one or more of: downloading a number of work items fromthe folder, changing a sorting option for the work items in the folder,or changing a different view style, or a combination thereof.
 14. Themethod of claim 1, wherein the target content comprises a folder, andwherein the access to the target content includes uploading a file tothe folder.
 15. The method of claim 14, further comprising: inspectingthe uploaded file; and performing actions on the uploaded file inresponse to a result from the inspecting.
 16. The method of claim 14,further comprising: preventing another software widget from accessingthe uploaded file.
 17. The method of claim 1, further comprising:receiving configuration parameters to customize the software widget. 18.The method of claim 17, wherein the customization includes layoutdefinitions for the software widget.
 19. The method of claim 17, whereinthe customization includes adjustment of functionalities of the softwarewidget in accessing the target content.
 20. The method of claim 1,further comprising: tracking access activities performed via eachsoftware widget to the target content.
 21. A computer server which hostsa cloud-based environment shared between a user and one or morecollaborators of the user, the server comprising: a processor; and amemory unit having instructions stored thereon which when executed bythe processor, causes the processor to: receive a request identifying atarget content that is shareable between the user and the collaboratorsof the user in the cloud-based platform, wherein the request includescustomizable functionalities associated with one or more available typesof access around the target content; automatically generate, by thecloud-based platform and based on said request, embeddable software codethat is embeddable in one or more software products for generating asoftware widget to provide access to the target content from the one ormore software products that are different from the cloud-based platformgenerating the embeddable software code, wherein generating theembeddable software code includes: receiving a user selection of afolder in the cloud-based environment to be embedded in the softwarewidget, the folder being accessible through the software widget and inthe cloud-based platform, receiving configuration parameters, theconfiguration parameters configuring the software widget to instruct thecloud-based environment to perform security related tasks on a fileuploaded to the folder via the software widget, the security relatedtasks including scanning and/or quarantining the file, and generatingthe embeddable software code based on the user selection and theconfiguration parameters; transmitting the embeddable software code to auser device associated with the user; receiving an indication at thecloud-based platform that the embeddable software code is embedded in asoftware product of the one or more software products; and generatingthe software widget in the software product in response to theembeddable software code being embedded in the software product, whereinsaid software widget provides the one or more available types of accessto the target content in accordance with the customizablefunctionalities included in the request.
 22. The server of claim 21,wherein the software widget is to be embedded in a software product soas to enable a user of the software product to access the target contentwithout navigating away from the software product.
 23. The server ofclaim 21, wherein the software widget is generated as a unique instance.24. The server of claim 21, wherein the embeddable software code areuniquely generated so that different software widgets generated in aplurality of instances can access the identified target content and eachhave a distinct configuration.
 25. The server of claim 21, wherein theprocessor is further configured to: prompt a user to preview thesoftware widget, wherein activation of the preview causes a web browserof the user to execute the software embeddable code.
 26. The server ofclaim 21, wherein the processor is further configured to: prompt a userto copy the software embeddable code into a memory on a device of theuser.
 27. The server of claim 21, wherein the embeddable software codeare configured to be directly included in a software product without acompilation process.
 28. The server of claim 21, wherein the softwareproduct is a webpage or a web application.
 29. The server of claim 21,wherein the request is received from a user, and wherein the processoris further configured to: present, via a user interface, embeddablesoftware code to the user.
 30. The server of claim 21, wherein thetarget content comprises a file, and wherein the access to the targetcontent includes one or more of: viewing the file, editing the file,commenting on the file, highlighting portions of the file, or sharingthe file, or a combination thereof.
 31. The server of claim 21, whereinthe target content comprises a folder, and wherein the access to thetarget content includes one or more of: displaying a list of work itemsin the folder, downloading a number of work items from the folder,changing a sorting option for the work items in the folder, or changinga different view style, or a combination thereof.
 32. The server ofclaim 21, wherein the target content comprises a folder, and wherein theaccess to the target content includes uploading a file to the folder.33. The server of claim 32, wherein the processor is further configuredto: inspect the uploaded file; and perform actions on the uploaded filein response to a result from the inspecting.
 34. The server of claim 32,wherein the processor is further configured to: prevent another softwarewidget from accessing the uploaded file.
 35. The server of claim 32,herein the processor is further configured to: receive configurationparameters to customize the software widget.
 36. The server of claim 35,wherein the customization includes layout definitions for the softwarewidget.
 37. The server of claim 35, wherein the customization includesadjustment of functionalities of the software widget in accessing thetarget content.
 38. The server of claim 21, wherein the processor isfurther configured to: track access activities performed via eachsoftware widget to the target content.
 39. A non-transitorymachine-readable storage medium having stored thereon Instructionswhich, when executed by a processor on a server, cause the processor to:receive a request identifying a target content that is in a cloud-basedplatform and is shareable between a user and one or more collaboratorsof the user, wherein the request includes customizable functionalitiesassociated with one or more available types of access around the targetcontent; automatically generate, by the cloud-based platform and basedon said request, embeddable software code that is embeddable in one ormore software products for generating a software widget to provideaccess to the target content from the one or more software products thatare different from the cloud-based platform generating the embeddablesoftware code, wherein generating the embeddable software code includes:receiving a user selection of a folder in the cloud-based platform to beembedded in the software widget, the folder being accessible through thesoftware widget and in the cloud-based platform, receiving configurationparameters, the configuration parameters configuring the software widgetto instruct the cloud-based platform to perform security related taskson a file uploaded to the folder via the software widget, the securityrelated tasks including scanning and/or quarantining the file, andgenerating the embeddable software code based on the user selection andthe configuration parameters; transmitting the embeddable software codeto a user device associated with the user; receiving an indication atthe cloud-based platform that the embeddable software code is embeddedin a software product of the one or more software products; andgenerating the software widget in the software product in response tothe embeddable software code being embedded in the software product,wherein said software widget provides the one or more available types ofaccess to the target content in accordance with the customizablefunctionalities included in the request, wherein the software widget isconfigured to enable a user of the software product to access the targetcontent without navigating away from the software product, and whereineach software widget is generated as a unique instance.
 40. A systemwhich hosts a cloud-based environment shared between a user and one ormore collaborators of the user, comprising: means for receiving arequest identifying a target content that is shareable between the userand the collaborators of the user in the cloud-based platform, whereinthe request includes customizable functionalities associated with one ormore available types of access around the target content; and means forautomatically generating, by the cloud-based platform and based on saidrequest, embeddable software code that is embeddable in one or moresoftware products for generating a software widget to provide access tothe target content from the one or more software products that aredifferent from the cloud-based platform generating the embeddablesoftware code, wherein generating the embeddable software code includes:receiving a user selection of a folder in the cloud-based platform to beembedded in the software widget, the folder being accessible through thesoftware widget and in the cloud-based platform, receiving configurationparameters, the configuration parameters configuring the software widgetto instruct the cloud-based platform to perform security related taskson a file uploaded to the folder via the software widget, the securityrelated tasks including scanning and/or quarantining the file, andgenerating the embeddable software code based on the user selection andthe configuration parameters; transmitting the embeddable software codeto a user device associated with the user; receiving an indication atthe cloud-based platform that the embeddable software code is embeddedin a software product of the one or more software products; andgenerating the software widget in the software product in response tothe embeddable software code being embedded in the software product,wherein said software widget provides the one or more available types ofaccess to the target content in accordance with the customizablefunctionalities included in the request.